Possible Duplicate:
How come verification does not include actual testing?

ISO norm 12207 states that testing is only validation activity, while all static inspections are verification (that requirement, code.. is complete, correct..). I did found some articles saying its not correct but you know, it is not "official". I would like to understand because there are two different concepts (in books & articles):
1) Verification is all testing except for UAT (because only user can really validate the use). E.g. here
OR
2) Verification is everything but testing. All testing is validation. E.g. here

Definitions are mostly the same, as Sommerville's:

The aim of verification is to check that the software meets its stated functional and non-functional requirements. Validation, however, is a more general process. The aim of validation is to ensure that the software meets the customer’s expectations. It goes beyond simply checking conformance with the specification to demonstrating that the software does what the customer expects it to do

It is really bugging me because I tend to agree that functional testing done on a product (SIT) is still verification because I just follow the requirements. But ISO does not agree..